I think that a standard is arising on the way a method is injected with a request bus. My naming was requestContext and I believe mach-ii and fusebox use both event. I think it would be benefitial for developers for me to change this to event. What are your thoughts on this? This would help if a developer wants to switch from one framework to another or doing a transition, if some of the similar elements shared in an MVC framework can remain the same. I am for changing it to event, but I would like to know you opinions?
Blog
Recent Entries
12 days of BoxLang - Day 3: SocketBox!
As BoxLang continues evolving into a modern, high-performance, JVM-based runtime, real-time communication becomes essential for the applications we all want to build: dashboards, collaboration tools, notifications, live feeds, multiplayer features, and more.
That’s where SocketBox steps in — the WebSocket upgrade listener built to work seamlessly with CommandBox and the BoxLang MiniServer. ⚡
Today, for Day 3, we’re highlighting how SocketBox supercharges BoxLang development by giving you fast, flexible, and framework-agnostic WebSocket capabilities.
Maria Jose Herrera
Maria Jose Herrera
December
12,
2025
12 Days of BoxLang - Day 2: CommandBox
BoxLang + CommandBox: The Enterprise Engine Behind Your Deployments
For Day 2 of our 12 Days of Christmas series, we’re diving into one of the most powerful parts of the BoxLang ecosystem: CommandBox the defacto enterprise servlet deployment platform for BoxLang.
If BoxLang is the language powering your applications, CommandBox is the engine room behind it all. ⚙️
Victor Campos
Victor Campos
December
11,
2025
12 Days of BoxLang - Day 1: ColdBox
ColdBox + BoxLang: The Future of Modern MVC on the JVM Welcome to Day 1 of the 12 Days of BoxLang
To kick off the series, we’re starting with one of the most powerful combinations in the Ortus ecosystem: ColdBox + BoxLang.
ColdBox has been the standard for modern CFML MVC development for over a decade. BoxLang is the next-generation dynamic language built for JVM and beyond. Together, they reshape how developers build web apps, APIs, microservices, CLIs, and soon desktop applications.
Let’s dive into why ColdBox 8 + BoxLang PRIME is a major milestone for the future of modern application development.
Maria Jose Herrera
Maria Jose Herrera
December
10,
2025
Add Your Comment
(5)
Feb 27, 2007 14:48:06 UTC
by Sana
Hi Luis, This makes perfect sense, should have some compatibility to other frameworks, at-least vocabulary should be same, so new developers adopt more easily.
Feb 27, 2007 16:20:13 UTC
by Sami Hoda
Can this be a customizable parameter instead?
Feb 27, 2007 18:07:03 UTC
by Luis Majano
I have been going over this and I think the best way is to just call the method and pass the argument. It would then be up to the developer to name the argument. However, the type of the argument will always be: coldbox.system.beans.requestContext How does this sound?
Feb 27, 2007 19:09:58 UTC
by Sami Hoda
I suppose that works. Whenever there is a chance for flexibility, I'm for it.
Mar 05, 2007 19:19:15 UTC
by tony petruzzi
Actually most of the other frameworks let you change the name to whatever you want, they just use event as the default. But you are correct when saying that this would make it alot easier to transition from one framework to another. BTW great work. ColdBox is getting more and more attention lately. I haven't heard anything coming out of the Model-Glue camp.